Skip to content

docs: add SourceWeft MCP Directory to community projects - #1858

Open
QThans wants to merge 1 commit into
modelcontextprotocol:mainfrom
QThans:docs/add-sourceweft-directory
Open

QThans wants to merge 1 commit into
modelcontextprotocol:mainfrom
QThans:docs/add-sourceweft-directory

Conversation

@QThans

@QThans QThans commented Nov 14, 2026

Copy link
Copy Markdown

Motivation and Context

Adds the SourceWeft MCP Directory to the "Browsers" section of the community projects list.

The directory at https://sourceweft.com/mcp is a web browser for the official MCP Registry: its entries are federated from registry.modelcontextprotocol.io (the sync lives in apps/backend/src/modules/market/federation.ts of the linked repository). Each server page shows the tools the server exposes where they can be listed, its auth and runtime details, and a connect guide. It is free to browse without an account, and the code is open source (Apache-2.0, with a separately licensed enterprise/ directory).

I am the maintainer of SourceWeft.

AI disclosure: this one-line change and description were drafted with an AI coding assistant; I reviewed and approved the submission.

How Has This Been Tested?

Documentation only. Checked that the link loads and that the line follows the format of the other entries in the section.

Breaking Changes

None.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant